Collection of Internet/Collection of Internet.iso/infosrvr/dev/www_talk.930/001314_daemon _Wed Jun 16 10:21:53 1993.msg

Internet Message Format | 1994-01-24 | 2KB

Received: by  nxoc01.cern.ch  (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
    id AA12302; Wed, 16 Jun 93 10:21:56 MET DST
Return-Path: <[e-mail]>
Received: from dxmint.cern.ch by  nxoc01.cern.ch  (NeXT-1.0 (From Sendmail 5.52)/NeXT-2.0)
    id AA12297; Wed, 16 Jun 93 10:21:53 MET DST
Received: from theory.CS.Mankato.MSUS.EDU by dxmint.cern.ch (5.65/DEC-Ultrix/4.3)
    id AA21685; Wed, 16 Jun 1993 10:44:02 +0200
Received: by theory.cs.mankato.msus.edu (5.65/DEC-Ultrix/4.3)
    id AA08704; Wed, 16 Jun 1993 03:44:23 -0500
Date: Wed, 16 Jun 1993 03:44:23 -0500
From: [e-mail] (Jay A. Carlson)
Message-Id: <[e-mail]>
To: [e-mail]
Cc: [e-mail], [e-mail]
In-Reply-To: Tim Berners-Lee's message of Wed, 16 Jun 93 10:04:22 +0200 <[e-mail]>
Subject: Resource estimation

> In fact, the load on an HTTP server machine is very slight,
> because the process only runs as long as it takes to return
> the document. The info.cern.ch server which has the Subject
> Catalogue gets probably a relatively high usage, about
> 10k requests a day, or (thinks...) one every 9 seconds.
> the CPU load is negligible.  In fact of course the peak rate
> is higher, but still its not really a factor.

Also note that httpd appears to be somewhat memory-hungry.  On my
DECstation 5000, running Ultrix, it used 8M to serve ONE PAGE.  In a
system serving more pages I can see that this kind of caching would be
useful, but in small systems you may wanna look at an alternative
server.

Jay Carlson
[e-mail]

Flat text is just *never* what you want.   ---stephen p spackman